Technologies for converting mobile communications network billing records

ABSTRACT

Technologies for converting mobile communications network billing records include a billing record converter system. The billing record converter system receives a data usage billing record associated with a mobile computing device communicatively coupled to a long term evolution wireless communications network. The received data usage billing record is formatted according to a real-time data usage billing record format. The received data usage billing record is converted into a new data usage billing record formatted according to a roaming data usage billing record format that corresponds to a legacy wireless communications network. The new data usage billing record is transmitted to a billing system of the legacy wireless communications network for processing. In some embodiments, the billing record converter system cumulates and converts multiple data usage billing records associated with the mobile computing device into the new data usage billing record. Other embodiments are described and claimed.

CROSS REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Provisional PatentApplication Ser. No. 62/081,785, filed on Nov. 19, 2014, entitled SYSTEMAND METHOD OF PROCESSING LTE USAGE DATA, the disclosure of which ishereby incorporated by reference in its entirety.

TECHNICAL FIELD

The technologies described below relate generally to the field ofconverting data usage billing records on 4G LTE networks into data usagerecords (e.g., records indicative of data received at a user's deviceand/or records indicative of data transmitted from a user's device) thatare compatible with 2G/3G billing systems. More particularly, thetechnologies relate to the field of processing 4G LTE 3rd GenerationPartnership Project Online Charging System (3GPP OCS) usage records intoTransferred Account Procedure (TAP) records that are received by 2G/3Gbilling systems as visited network usage billing records.

BACKGROUND

Wireless communication providers are increasingly upgrading legacycommunication networks to support newer communication standards andequipment. For example, second generation (2G) and third generation (3G)wireless networks are being upgraded to simultaneously support fourthgeneration (4G) communication standards and network elements. However,4G network elements use different data usage records that are generallynot compatible with existing billing systems for 2G and 3G wirelessnetworks. As such, wireless communication providers typically must incurthe cost of a separate billing system or billing software module for 4Gwireless networks as part of an upgrade.

SUMMARY

In an embodiment, the present disclosure is directed, in part, to amethod for converting mobile communications network billing records. Themethod includes receiving, by a billing record converter system, a firstdata usage billing record associated with a mobile computing devicecommunicatively coupled to a long term evolution (LTE) wirelesscommunications network. The first data usage billing record can beformatted according to a real-time data usage billing record format. Themethod also includes converting, by the billing record converter system,the first data usage billing record formatted according to the real-timedata usage billing record format into a second data usage billing recordformatted according to a roaming data usage record format. The roamingdata usage record format can correspond to a legacy wirelesscommunications network different from the LTE wireless communicationsnetwork. Further, the method includes transmitting, by the billingrecord converter system, the second data usage billing record to abilling system of the legacy wireless communications network forprocessing.

In some embodiments of the method, the real-time data usage billingrecord format is a 3rd generation partnership project online chargingsystem format and the roaming data usage record format is a TransferredAccount Procedure (TAP) format. Additionally, in some embodiments of themethod, the legacy wireless communications network is a third generation(3G) wireless communications network. In embodiments of the method,transmitting the second data usage billing record to the billing systemof the legacy wireless communications network can include transmittingthe second data usage billing record to a roaming data usage recordexchanger of the legacy wireless communications network for forwardingto the billing system.

Additionally, in some embodiments, the method includes receiving, by thebilling record converter system and during a communications session,additional data usage billing records associated with the mobilecomputing device communicatively coupled to the LTE wirelesscommunications network. In such embodiments, the additional data usagebilling records can be formatted according to the real-time data usagebilling record format. The method of such embodiments can furtherinclude cumulating, by the billing record converter system, the firstdata usage billing record and the additional data usage billing recordsreceived during the communications session into a cumulated data usagebilling record formatted according to the real-time data usage billingrecord format. Additionally, in such embodiments, the method includesdetermining, by the billing record converter system, whether thecommunications session of the mobile computing device communicativelycoupled to the LTE wireless communications network has ended. In suchembodiments of the method, converting the first data usage billingrecord into the second data usage billing record can include converting,in response to a determination that the communications session hasended, the cumulated data usage billing record formatted according tothe real-time data usage billing record format into the second datausage billing record formatted according to the roaming data usagerecord format.

Further, in some embodiments, the method can also include receiving, bythe billing record converter system and during a communications session,additional data usage billing records associated with the mobilecomputing device communicatively coupled to the LTE wirelesscommunications network. The additional data usage billing records can beformatted according to the real-time data usage billing record format.In such embodiments, the method further includes cumulating, by thebilling record converter system, the first data usage billing record andthe additional data usage billing records received during thecommunications session into a cumulated data usage billing recordformatted according to the real-time data usage billing record format.The method of such embodiments also includes determining, by the billingrecord converter system, an amount of data used by the mobile computingdevice during the communications session based on the first data usagebilling record and the additional data usage billing records receivedduring the communications session. Further, the method of suchembodiments includes determining, by the billing record convertersystem, whether the determined amount of data used by the mobilecomputing device during the communications session satisfies a referencedata usage threshold. In such embodiments of the method, converting thefirst data usage billing record into the second data usage billingrecord can include converting, in response to a determination that thedetermined amount of data used by the mobile computing device satisfiesthe reference data usage threshold, the cumulated data usage billingrecord formatted according to the real-time data usage billing recordformat into the second data usage billing record formatted according tothe roaming data usage record format.

In some embodiments, the method further includes determining, by thebilling record converter system, a predicted amount of data to be usedby the mobile computing device during the communications session basedat least in part on historical data usage patterns of the mobilecomputing device and configuring, by the billing record convertersystem, the reference data usage threshold as a function of thepredicted amount of data to be used by the mobile computing deviceduring the communications session. In other embodiments, the method alsoincludes determining, by the billing record converter system, apredicted amount of data to be used by the mobile computing deviceduring the communications session based at least in part on historicaldata usage patterns of other mobile computing devices communicativelycoupled to the LTE wireless communications network and configuring, bythe billing record converter system, the reference data usage thresholdas a function of the predicted amount of data to be used by the mobilecomputing device during the communications session. Alternatively, themethod can further include determining, by the billing record convertersystem, a type of the communications session associated with first datausage billing record and the additional data usage billing records andmodifying, by the billing record converter system, the reference datausage threshold based at least in part on the determined type of thecommunications session. In other embodiments, the method can includedetermining, by the billing record converter system, an amount of timeelapsed for the communications session and modifying, by the billingrecord converter system, the reference data usage threshold based atleast in part on the determined amount of time elapsed for thecommunications session.

In another embodiment, the present disclosure is directed, in part, to asystem for converting mobile communications network billing records. Thesystem includes a billing record converter system having a processorexecuting instructions stored in memory. The instructions, whenexecuted, cause the processor to receive a first data usage billingrecord associated with a mobile computing device communicatively coupledto a long term evolution (LTE) wireless communications network. Thefirst data usage billing record can be formatted according to areal-time data usage billing record format. The instructions also causethe processor to convert the first data usage billing record formattedaccording to the real-time data usage billing record format into asecond data usage billing record formatted according to a roaming datausage record format, the roaming data usage record format corresponds toa legacy wireless communications network different from the LTE wirelesscommunications network. Additionally, the instructions cause theprocessor to transmit the second data usage billing record to a billingsystem of the legacy wireless communications network for processing.

In some embodiments, the real-time data usage billing record format canbe a 3rd generation partnership project online charging system formatand the roaming data usage record format can be a Transferred AccountProcedure (TAP) format. Additionally or alternatively, the legacywireless communications network is a third generation (3G) wirelesscommunications network. Additionally, in some embodiments, theinstructions to transmit the second data usage billing record to thebilling system of the legacy wireless communications network includeinstructions to transmit the second data usage billing record to aroaming data usage record exchanger of the legacy wirelesscommunications network for forwarding to the billing system.

Additionally, in some embodiments, the instructions further cause theprocessor of the billing record converter system to receive, during acommunications session, additional data usage billing records associatedwith the mobile computing device communicatively coupled to the LTEwireless communications network. The additional data usage billingrecords can be formatted according to the real-time data usage billingrecord format. In such embodiments, the instructions also cause theprocessor to cumulate the first data usage billing record and theadditional data usage billing records received during the communicationssession into a cumulated data usage billing record formatted accordingto the real-time data usage billing record format. The instructions ofsuch embodiments further cause the processor to determine whether thecommunications session of the mobile computing device communicativelycoupled to the LTE wireless communications network has ended. In suchembodiments, the instructions to convert the first data usage billingrecord into the second data usage billing record include instructions toconvert, in response to a determination that the communications sessionhas ended, the cumulated data usage billing record formatted accordingto the real-time data usage billing record format into the second datausage billing record formatted according to the roaming data usagerecord format.

In some embodiments, the instructions of the billing record convertersystem further cause the processor to receive, during a communicationssession, additional data usage billing records associated with themobile computing device communicatively coupled to the LTE wirelesscommunications network. The additional data usage billing records can beformatted according to the real-time data usage billing record format.The instructions of such embodiments can further cause the processor tocumulate the first data usage billing record and the additional datausage billing records received during the communications session into acumulated data usage billing record formatted according to the real-timedata usage billing record format. Additionally, in such embodiments, theinstructions can further cause the processor to determine an amount ofdata used by the mobile computing device during the communicationssession based on the first data usage billing record and the additionaldata usage billing records received during the communications session.The instructions of such embodiments can also cause the processor todetermine whether the determined amount of data used by the mobilecomputing device during the communications session satisfies a referencedata usage threshold. In such embodiments, the instructions to convertthe first data usage billing record into the second data usage billingrecord include instructions to convert, in response to a determinationthat the determined amount of data used by the mobile computing devicesatisfies the reference data usage threshold, the cumulated data usagebilling record formatted according to the real-time data usage billingrecord format into the second data usage billing record formattedaccording to the roaming data usage record format.

Additionally, in some embodiments, the instructions of the billingrecord converter system can also cause the processor to determine apredicted amount of data to be used by the mobile computing deviceduring the communications session based at least in part on historicaldata usage patterns of the mobile computing device and configure thereference data usage threshold as a function of the predicted amount ofdata to be used by the mobile computing device during the communicationssession. In other embodiments, the instructions cause the processor todetermine a predicted amount of data to be used by the mobile computingdevice during the communications session based at least in part onhistorical data usage patterns of other mobile computing devicescommunicatively coupled to the LTE wireless communications network andconfigure the reference data usage threshold as a function of thepredicted amount of data to be used by the mobile computing deviceduring the communications session. In yet other embodiments, theinstructions can further cause the processor to determine a type of thecommunications session associated with first data usage billing recordand the additional data usage billing records and modify the referencedata usage threshold based at least in part on the determined type ofthe communications session. Additionally or alternatively, in someembodiments, the instructions cause the processor to determine an amountof time elapsed for the communications session and modify the referencedata usage threshold based at least in part on the determined amount oftime elapsed for the communications session

BRIEF DESCRIPTION OF THE DRAWINGS

It is believed that certain embodiments will be better understood fromthe following description taken in conjunction with the accompanyingdrawings, in which like references indicate similar elements and inwhich:

FIG. 1 is a simplified network diagram of at least one embodiment of a2G/3G billing system for processing 2G and/or 3G data usage records thatcorrespond to data usage by a mobile computing device on a 2G and/or 3Gwireless communications network;

FIG. 2 is a simplified network diagram of at least one embodiment of abilling record converter system for converting 4G data usage recordsthat correspond to data usage by a mobile computing device on a 4Gwireless communications network into a format suitable for processing bythe 2G/3G billing system of FIG. 1;

FIG. 3 is a simplified block diagram of at least one embodiment of a 4Gwireless communications network element that includes the billing recordconverter system of FIG. 2;

FIG. 4 is a simplified flow diagram of at least one embodiment of amethod that may be executed by the billing record converter system ofFIGS. 2 and 3 for converting 4G data usage records into a formatsuitable for processing by the 2G/3G billing system of FIG. 1; and

FIG. 5 is a simplified block diagram of at least one embodiment of thebilling record converter system of FIGS. 2 and 3.

DETAILED DESCRIPTION

Various non-limiting embodiments of the present disclosure will now bedescribed to provide an overall understanding of the principles of thestructure, function, and use of systems and methods disclosed herein.One or more examples of these non-limiting embodiments are illustratedin the selected examples disclosed and described in detail withreference made to the figures in the accompanying drawings. Those ofordinary skill in the art will understand that systems and methodsspecifically described herein and illustrated in the accompanyingdrawings are non-limiting embodiments. The features illustrated ordescribed in connection with one non-limiting embodiment may be combinedwith the features of other non-limiting embodiments. Such modificationsand variations are intended to be included within the scope of thepresent disclosure.

The systems, apparatuses, devices, and methods disclosed herein aredescribed in detail by way of examples and with reference to thefigures. The examples discussed herein are examples only and areprovided to assist in the explanation of the apparatuses, devices,systems and methods described herein. None of the features or componentsshown in the drawings or discussed below should be taken as mandatoryfor any specific implementation of any of these the apparatuses,devices, systems or methods unless specifically designated as mandatory.In addition, elements illustrated in the figures are not necessarilydrawn to scale for simplicity and clarity of illustration. For ease ofreading and clarity, certain components, modules, or methods may bedescribed solely in connection with a specific figure. In thisdisclosure, any identification of specific techniques, arrangements,etc. are either related to a specific example presented or are merely ageneral description of such a technique, arrangement, etc.Identifications of specific details or examples are not intended to be,and should not be, construed as mandatory or limiting unlessspecifically designated as such. Any failure to specifically describe acombination or sub-combination of components should not be understood asan indication that any combination or sub-combination is not possible.It will be appreciated that modifications to disclosed and describedexamples, arrangements, configurations, components, elements,apparatuses, devices, systems, methods, etc. can be made and may bedesired for a specific application. Also, for any methods described,regardless of whether the method is described in conjunction with a flowdiagram, it should be understood that unless otherwise specified orrequired by context, any explicit or implicit ordering of stepsperformed in the execution of a method does not imply that those stepsmust be performed in the order presented but instead may be performed ina different order or in parallel.

Reference throughout the specification to “various embodiments,” “someembodiments,” “one embodiment,” “some example embodiments,” “one exampleembodiment,” or “an embodiment” means that a particular feature,structure, or characteristic described in connection with any embodimentis included in at least one embodiment. Thus, appearances of the phrases“in various embodiments,” “in some embodiments,” “in one embodiment,”“some example embodiments,” “one example embodiment,” or “in anembodiment” in places throughout the specification are not necessarilyall referring to the same embodiment. Furthermore, the particularfeatures, structures or characteristics may be combined in any suitablemanner in one or more embodiments.

Throughout this disclosure, references to components or modulesgenerally refer to items that logically can be grouped together toperform a function or group of related functions. Like referencenumerals are generally intended to refer to the same or similarcomponents. Components and modules can be implemented in software,hardware, or a combination of software and hardware. The term “software”is used expansively to include not only executable code, for examplemachine-executable or machine-interpretable instructions, but also datastructures, data stores and computing instructions stored in anysuitable electronic format, including firmware, and embedded software.The terms “information” and “data” are used expansively and includes awide variety of electronic information, including executable code;content such as text, video data, and audio data, among others; andvarious codes or flags. The terms “information,” “data,” and “content”are sometimes used interchangeably when permitted by context. It shouldbe noted that although for clarity and to aid in understanding someexamples discussed herein might describe specific features or functionsas part of a specific component or module, or as occurring at a specificlayer of a computing device (for example, a hardware layer, operatingsystem layer, or application layer), those features or functions may beimplemented as part of a different component or module or operated at adifferent layer of a communication protocol stack. Those of ordinaryskill in the art will recognize that the systems, apparatuses, devices,and methods described herein can be applied to, or easily modified foruse with, other types of equipment, can use other arrangements ofcomputing systems such as client-server distributed systems, and can useother protocols, or operate at other layers in communication protocolstacks, than are described.

The billing record converter technologies disclosed herein facilitatethe deployment of 4G Long Term Evolution (4G LTE) network elements intoexisting carrier networks. It should be appreciated that in addition tofacilitating the deployment of existing 4G LTE network elements intoexisting carrier networks, the billing record converter technologiesdisclosed herein can also facilitate the deployment of future evolutionsof 4G LTE network elements into existing carrier networks. 4G LTEnetwork elements use different data usage records that are generally notcompatible with existing billing systems for 2G and 3G networks. Thebilling record converter technologies permit existing 2G and 3G billingsystems to receive data usage records from 4G LTE network elements inthe Transferred Account Procedure (TAP) record format. The data usagerecords from a 4G LTE network element are first converted into the TAPrecord format and then fed back to the billing system using the inboundTAP record Application Programming Interface (TAP record API) of thebilling system. The TAP record API is intended for receiving data usagerecords for roaming subscribers in visited networks. By converting thedata usage records of a 4G LTE network element into the TAP recordformat, the wireless service provider's billing systems can receive datausage records from a 4G LTE network elements as if those data usagerecords were roaming subscriber data usage records, even though thesubscriber can be in the home network on a local 4G LTE network. Thebilling record converter technologies advantageously allow a wirelessservice provider to migrate to 4G LTE networks while continuing to usethe wireless service provider's existing billing systems. The wirelessservice provider can run both 4G LTE and 2G or 3G networks using thesame billing systems. A wireless service provider, or carrier, candeploy 4G LTE network elements and quickly provide 4G LTE service towireless subscribers without incurring the cost of a separate billingsystem for their 4G LTE network.

The billing record converter technologies disclosed herein can also beconfigured to convert received data usage records formatted according toa new or enhanced data usage record format into data usage recordsformatted according to a previous or legacy data usage record format.For example, in some embodiments, the billing record convertertechnologies disclosed herein can be configured to convert data usagerecords received according to the GSMA TAP 3.12 (ver. 32.3) FormatSpecification (e.g., TAP 3.12 records) into data usage records formattedaccording to GSMA TAP 2 Format Specification (e.g., TAP 2 records). Indoing so, the billing record converter technologies disclosed herein candown-convert received billing records into a format compatible withlegacy billing systems and components thereof (e.g., a legacy TAP API).It should be appreciated that the billing record converter technologiesdisclosed herein can convert billing records to and from any otherspecification formats.

The billing record converter technologies can analyze data usagepatterns and determine a predicted data usage for a user. The predicteddata usage can be used to determine the amount of data billed in eachdata usage record. By setting the amount of data billed in each datausage record to approximately the predicted amount of data to be used bythe user, the billing record converter technologies advantageouslyreduces the number of data usage records produced. Reducing the numberof data usage records that are produced reduces the total bill volumewhich in turn reduces the cost of operating downstream billing systems.The billing record converter technologies can similarly be employed toreduce the number of billing records generated by 4G LTE systems thatare sent to 4G LTE billing systems.

Additionally, in some embodiments, the billing record convertertechnologies disclosed herein can be configured to receive confirmationsignaling from one or more Mobile Edge Computing (MEC) applications thatexecute or operate within a data tunnel between the EPC and an EvolvedNode B (eNodeB) or other wireless network element. In such embodiments,the billing record converter technologies disclosed herein (e.g., thebilling record converter system 210 of FIG. 2) can determine the contentidentifier (content ID), Categorized QoS, and a data count of contentassociated with such applications. Additionally, the billing recordconverter technologies can release one or a defined set of billingrecords associated with such content based at least in part on, orotherwise as a function of, an authorized content ID, Categorized QoS,and/or a predetermined or reference data volume count associated withthe content. It should be appreciated that billing record convertertechnologies disclosed herein can also be configured to receive andprocess any other type of signaling and data associated with MECapplications, components, and/or entities as currently defined, ordefined in the future, by the Mobile-Edge Computing IndustrySpecification Group or any other group or committee.

In some embodiments, the billing record converter technologies disclosedherein can also be configured to apply one or more deterministic billcreation rules after receiving signaling from any Voice over LTE (VoLTE)element through IMS signaling working within a data tunnel from the IMSthrough the EPC, eNodeB, and to an application within the UE.Additionally, the billing record converter technologies can beconfigured to apply one or more deterministic bill creation rules afterreceiving signaling associated with Device-to-Device (Proximity Serviceor “ProSe”) direct user traffic communications defined in 3GPP Release12 specifications. In some embodiments, only signaling passing throughto a ProSe function within the EPC can be processed.

FIG. 1 depicts a network diagram of an example 2G network and/or 3Gnetwork. A wireless subscriber can use their mobile computing device102, such as a cell phone or smart phone that supports a 2G or 3Gnetwork protocol, to place a call or use data on their home network 100.A radio tower 104, such as a cellular radio tower supporting 2G and/or3G network protocols, can transmit data to, and receive data from, themobile computing device 102 using a suitable radio frequency andprotocol, such as the general packet radio service, or GPRS, running onan 850 MHz code division multiple access, or CDMA network, at 1×RTT orEV-DO speeds. Other frequencies and protocols can be used as would beunderstood by one of ordinary skill in the art.

In the example home network 100 of FIG. 1, when the wirelesssubscriber's mobile computing device 102 uses data on the home network100, a GPRS support node 106 sends a session detail record, or SDR 108,to a billing system 110. The billing system 110 can load rating datainto the wireless subscriber's bill for the data usage by the wirelesssubscriber's mobile computer device 102. The GPRS support node 106 canbe a Gateway GPRS support node or a Serving GPRS support node as wouldbe understood in the art.

The billing system 110 also includes a TAP record applicationprogramming interface, or TAP record API, that can receive billingrecords called TAP records 122 from other networks when a wirelesssubscriber uses the mobile computing device 102 in a visited network112. The billing system 110 can include an inbound TAP record API forreceiving TAP records 122 from wireless providers of the visitednetworks 112, called visited network operators (or VPMN as per theinternational naming convention for visited network operators). Thebilling system 110 can include an outbound TAP record API for sendingTAP records 122 from the wireless provider of the home network 100,called the home network operator (or HPMN as per the internationalnaming convention for home network operators) to another wirelessnetwork operator. A TAP record 122 can use the TAP3 format, orTransferred Account Procedure Data Record Format Specification, VersionNo. 3, which is an international standard that facilitates theinteroperability of wireless mobile computing devices across networks100, 112. The TAP record 122 can also use previous versions of TAP,future versions of TAP, or any other suitable type of record format aswould be understood by one of ordinary skill in the art.

When the mobile computing device 102 of a wireless subscriber moves fromthe subscriber's home network 100 into a visited network 112, asillustrated by the dotted line of FIG. 1, the mobile computing device102 will begin to transmit and receive data from a radio tower 114 inthe visited network 112. The visited GSN 116 can authenticate the mobilecomputing device 102 and allow the wireless subscriber to roam in thevisited network 112. The GSN 116 can send one or more session detailrecords, or SDR 118, to the billing system 120 of the visited network112. Because the roaming wireless subscriber is not a customer of thewireless service provider of the visited network, or visited networkoperator, the billing system 120 cannot bill the wireless subscriberdirectly. The billing system 120 will forward a TAP record 122 to a TAPrecord exchanger 124, which can be a third party settlement agency suchas Syniverse™. The TAP record exchanger 124 can send the TAP record 122to the appropriate wireless service provider for billing the wirelesssubscriber. For example, the TAP record exchanger 124 can send the TAPrecord 122 to the inbound TAP record API of the billing system 110 inthe wireless subscriber's home network 100. In an embodiment, theinformation in the TAP record 122 received by the TAP record exchanger124 is the same as the information in the TAP record 122 that is sent tothe inbound TAP record API of the billing system 110. In an embodiment,the TAP record exchanger 124 can modify information in the TAP record122 prior to sending the TAP record 122 to the inbound TAP record API ofthe billing system 110. In a configuration, multiple TAP records 122 canbe sent between billing systems 110, 120 and the TAP record exchanger124.

Referring now also to FIG. 2, a billing record converter system 210 canallow a wireless service provider to offer 4G LTE service in a homenetwork 200, but continue to use the existing billing system 110.Wireless subscribers using 2G or 3G mobile computing devices 102 cancontinue to use the 2G or 3G radio towers 104, and the GPRS support node106 can send SDRs 108 to the billing system 110 as described in FIG. 1.Wireless subscribers using newer mobile computing devices 202 thatsupport the 4G LTE protocol can communicate with radio towers 204 thatsupport 4G LTE services. In a configuration, the same physical radiotower 104 can be used with different electronics and antennae to support4G LTE service. A 4G LTE network element 206 in the 4G LTE network caninclude a packet data network (PDN) gateway, or PGW, and a servinggateway, or SGW, among other modules.

The new 4G LTE network elements send billing records using a standardcalled 3GPP OCS, or 3rd generation partnership project online chargingsystem, that permits communication service providers such as wirelessservice providers to charge wireless subscribers in real time. The 4GLTE network element 206 can create 3GPP OCS records 208 based on thedata usage of the mobile computing device 202 on the 4G LTE network. Awireless service provider's billing system 110 for 2G and 3G networksgenerally cannot natively support 3GPP OCS records 208. To overcome thislimitation, the billing record converter system 210 can receive the 3GPPOCS records 208 from the 4G LTE network element 206, and create one ormore new TAP records 212 that are sent to the billing system 110. Thebilling system 110 therefore receives these new TAP records 212associated with the mobile computing device 202 on the new 4G LTEnetwork as if the mobile computing device 202 was roaming on the 2G or3G visited network 112 of FIG. 1. The billing record converter system210 can be a blade server that physically resides in the 4G LTE networkelement 206 and interfaces with other modules such as the PGW 306 andSGW 308 across a backplane, as illustrated in FIG. 3 and as described infurther detail below. In various embodiments, the billing recordconverter system 210 can be a standalone server, a cloud based service,a blade server that resides in other 4G LTE equipment, one or moreprocesses executing in the 4G LTE network element 206, for example theMME 302 of FIG. 3, or another suitable hardware platform or softwaremodule as would be generally understood by one of ordinary skill in theart.

Referring now also to FIG. 3, an example 4G LTE network element 300 ispresented. The 4G LTE network element 300 can include modules forsupporting the evolved packet core, or EPC protocol stack, of the 4G LTEnetwork. A mobile management entity, or MME 302, controls the connectionof user equipment, or UE, such as the mobile computing devices 202 ofFIG. 2 to the 4G LTE network. A home subscriber service, or HSS module304, identifies and authenticates UE on the home network. A servinggateway, or SGW 308, and a packet data network (PDN) gateway, or PGW306, connect the UE to a network, such as the Internet. A policy andchange function, or PCRF 310, prioritizes certain types of data overother types of data. For example, the PCRF 310 prioritizes voice data toensure low latency reliable delivery.

Other modules 312, 314 store configuration and general contentincluding, for example, elements of MEC applications, paymentapplications, pre-paid content, push advertisements/promotional content,profile triggered content, location service triggered content, and/oraccess method triggered content, all of which are as defined andunderstood by one of ordinary skill in the art. Additionally oralternatively, the other modules 312, 314 can perform caching functions.A TAP server blade 316 can perform the billing record converter system210 described above in reference to FIG. 2, for example by receiving3GPP OCS records, creating TAP records, and forwarding the TAP recordsto a billing system, third party settlement agency, or other suitablesystem. An example TAP server blade 316 is described in further detailwith regard to FIG. 5 below.

Referring now to FIG. 4, example operations of the billing recordconverter system 210 are shown. Processing begins at start block 400labeled START and continues to process block 402.

In process block 402, the billing record converter system 210 receivesdata usage detail records 208 from a 4G LTE network element 206. Forexample, the data usage detail records 208 can be one or more 3GPP OCSrecords 208. The 3GPP OCS records 208 can be associated with a mobilecomputing device, for example a mobile computing device 202 that is inthe home network 200 of a wireless service provider. In a configuration,the data usage detail record 208 can be a session detail record (SDR).Processing continues to decision block 404.

In decision block 404, if wireless subscriber has an unlimited dataplan, then processing continues to decision block 406; otherwise, if thewireless subscriber is on a pay-per-use data plan then processingcontinues to decision block 420. Additionally, in decision block 404, ifa MEC application is associated with an authorized Content ID,Categorized QoS, and volume count and/or if the wireless subscriber isengaged in a VoLTE session or a Device-to-Device session, thenprocessing also continues to decision block 406, in some embodiments. Insuch embodiments, one or more deterministic rules can be applied tomanage the number of billing records.

In decision block 406, if the wireless usage of a wireless subscriberwith an unlimited data plan is tracked, then processing continues toprocess block 408, otherwise processing returns to process block 402 toreceive additional data usage detail records such as 3GPP OCS records208.

In process block 408, the data usage of a wireless subscriber with anunlimited data plan can be tracked. For example, a commerciallyavailable EPC protocol stack (the Evolved Packet Core protocol stackused in 4G LTE networks) can include metering software that includes acounter. For a wireless subscriber with an unlimited data plan, the datausage can be cumulated until the end of a session for the wirelesssubscriber and then a single data usage record (e.g., TAP 212) can besent in process block 414. In various embodiments, the data usage recordcan be a TAP record 212, a 3GPP OCS record 208, or another suitable datausage record. For example, in the illustrative embodiment, the datausage record is a TAP 3.12 (version 32.3) record. In other examples, thedata usage record can be formatted according to a previous version ofthe TAP Format Specification or more current version of the TAP FormatSpecification. Advantageously, this can substantially reduce the numberof TAP records 212 or other data usage records that are sent to thebilling system 110, while permitting tracking of the wirelesssubscriber's data usage. Reducing the number of records sent to thebilling system 110 can reduce operating costs of the billing system 110and reduce third party charges for records forwarded to other serviceproviders or billing processors. Processing continues to decision block410.

In decision block 410, if the wireless subscriber with an unlimited dataplan has ended the data session, then processing continues to processblock 412 where a TAP record 212 and/or other data usage record can becreated. Otherwise, processing returns to process block 402 to receiveadditional data usage records, such as 3GPP OCS records 208, for thedata session of the wireless subscriber.

In process block 412, the billing record converter system 210 can createTAP records 212 for the data used by the wireless subscriber. In anembodiment, a data usage record compatible with a 4G LTE billing systemcan be created in parallel or instead of creating a TAP record 212. Inthat embodiment, the process steps described herein can includeoperations of sending and receiving data usage records to 4G LTE billingsystems in addition to or instead of TAP records 112. Processingcontinues to process block 414.

In process block 414, the billing record converter system 210 sends theTAP record 212 to an appropriate system. For example, the billing recordconverter system 212 can transmit the TAP record 212 to the inbound TAPrecord API of the billing system 110 or some other 2G/3G billing system.Processing continues to process block 416.

In process block 416, the TAP record 212 from process blocks 412 and 414can be received. For example, the billing system 110 (or another 2G/3Gbilling system) can receive the TAP record 212 on the inbound TAP recordAPI of the billing system 110. Processing continues to decision block418.

In decision block 418, if more data usage records (e.g., 3GPP OCSrecords 208) are to be received by the billing record converter system210, the processing returns to process block 402 to receive additionaldata usage records from the 4G LTE network element 206. Otherwise,processing terminates in end bock 428 labeled END.

In decision block 420, if the data usage of the wireless subscriber on apay-per-use data plan needs to be estimated, for example if the wirelesssubscriber initiated a new data or communications session, thenprocessing continues to process block 422.

In process block 422, the data usage of a wireless subscriber isestimated. For example, a commercially available EPC protocol stack(e.g., the Evolved Packet Core protocol stack used in 4G LTE networks)can include metering software that includes a configurable counter or aconfigurable reference data usage threshold. The metering software candetermine the configurable counter or reference data usage thresholdaccording to the anticipated data usage of the wireless subscriber. Themetering software can determine, or predict, the anticipated data usagebased on previous usage patterns of the wireless subscriber and/or themobile computing device 202, the application being used by the wirelesssubscriber, and the data usage of other subscribers and/or other mobilecomputing devices, among other example usage patterns as would beunderstood by one of ordinary skill in the art. In a configuration, theconfigurable counter and/or configurable reference data usage thresholdcan default to a common size for all wireless subscribers or UE (userentity, such as a mobile computing device or smartphone.) For example,the configurable counter and/or reference data usage threshold can beconfigured to 400 k, and a new TAP record 212 can be sent in processblock 412 for every 400 k of data used by the wireless subscriber with apay-per-use data plan. In another configuration, the configurablecounter and/or reference data usage threshold can be smaller or largerdepending upon, at least in part, trending information about thewireless subscriber that is available to the system, or typical wirelesssubscriber usage profiles.

For example, the configurable counter and/or reference data usagethreshold for a new wireless subscriber to the system can be configuredto be 200 k, initially. If additional information about the wirelesssubscriber is available, then the configurable counter and/or referencedata usage threshold can be based on historical patterns for thewireless subscriber. For example, the previous five data sessions for awireless subscriber can be averaged to determine the initialconfiguration of the configurable counter/threshold. In a configuration,if the user is executing a particular service, for example emailsynchronizing, then the initial configuration of the configurablecounter and/or reference data usage threshold can be set to a valueappropriate for that service. In various configurations, theconfiguration of the configurable counter/threshold can be ramped up ordown based on any suitable factors including, but not limited to, thetype of session, the website visited, whether an application is anapplication that pushes or pulls data, the ongoing amount of time spenton the same website or the same session, and so forth. In aconfiguration, the configurable counter and/or reference data usagethreshold can dynamically change as the wireless subscriber's usechanges. For example, the configurable counter/threshold can dynamicallychange based on the application the wireless subscriber uses, forexample by using the average data usage for the last five instances thesubscriber used the application. Other suitable configurations are alsocontemplated. The wireless subscriber's historical patterns can bestored in the HSS module 304 of the 4G LTE network element 300 of FIG.3.

In an embodiment, trending and other suitable information stored in theHSS module 304 can be shared with other 4G LTE network elements. In thisway, trending information available to one 4G LTE network element can beshared so that each 4G LTE network element can benefit from the trendinginformation generated by other 4G LTE network elements for wirelesssubscribers. For example, when a wireless subscriber is roaming, theroaming 4G LTE networks elements can receive trending and otherinformation about the wireless subscriber's data usage from the homearea HSS module 304. The information can be transmitted to the roaming4G LTE network elements using HSS messages sent via 4G LTE signalingnetworks, such as those used in Diameter Signaling as would beunderstood in the art. Similarly, trending and other information forinbound roaming wireless subscribers entering the home network can bereceived by the billing record converter system 210 and used to set thedata usage size for creating billing records. Processing continues toprocess block 412 where a TAP record 212 for the initial data use iscreated.

In process block 422, if the data usage of the wireless subscriber ofdecision block 420 did not need to estimated, adjusted, or re-estimated,then the current data use of the wireless subscriber is cumulated, forexample using the configurable counter and/or reference data usagethreshold of process block 422. Processing continues to decision block426.

In decision block 426, if data usage of the wireless subscribercumulated in process block 424 has not exceeded the estimated data usageconfigured in the configurable counter and/or reference data usagethreshold, then processing continues to decision block 410 where adetermination can be made as to whether the session has ended (andtherefore whether a TAP record 212 in process block 412 can be created).Otherwise, if the data usage of the wireless subscriber has exceededestimated data usage, then a new TAP record 212 can be created andprocessing continues to process block 412. The billing record convertersystem 210 can adjust the configurable counter or data usage to reflectthe amount billed to the wireless subscriber in the TAP record 212 ofprocess block 412. For example, the billing record converter system 210can subtract the amount billed in the TAP record 212 from the currentcumulated usage data. In another example, the billing record convertersystem 210 can re-estimate the data usage in decision block 420. Othersuitable means of keeping track of the ongoing data usage and the billeddata usage can be used as well as would be understood by one of ordinaryskill in the art.

Although the processes described above generally refer to creating areduced set of TAP records 212, similar processes can also be used toreduce the number of 4G LTE billing records. Advantageously, thedescribed processes can substantially reduce the number of data usagerecords that are sent to either or both 2G/3G and 4G LTE billingsystems. For example, in an embodiment, software executing in the 4G LTEnetwork element 206 can use a similar methodology to that describedabove to determine when to create a new data usage record, such as a3GPP OCS record 208. In another embodiment, the billing record convertersystem 210 can receive 3GPP OCS records 208 and create a reduced numberof 3GPP OCS records 208 that are sent to 4G LTE billing systems. In ahome network 200, the described processes can reduce the operatingexpense of the 4G LTE billing system by reducing the number of datausage records that need to be processed. When a wireless subscriber isin a visited network, 3GPP OCS or other data usage records can be sentto a third party billing processor for routing to the appropriatebilling system. Reducing the number of records can substantially reducethe transaction costs associated with third party billing processors astransaction costs are generally based on the number of recordsprocessed. Reducing the number of data usage records can also decreasethe required bandwidth necessary to transport the data usage records,allowing for additional savings in terms of network costs.

In an embodiment, a billing record converter system and the processesand the technologies described above can be utilized to allow a 2G/3Gwireless service provider to initially deploy 4G LTE network elementsinto the wireless service provider's network that can interoperate withexisting 2G/3G billing systems. Additionally, the billing recordconverter system and/or the processes described above can improve theoperation of, and reduce costs associated with operating, 4G LTE billingsystems as they are deployed. Therefore, the solutions described hereinare applicable to both migrations of 2G/3G networks to 4G LTE networks,and improving the operation of native 4G LTE networks in general.

The processes described above can be performed on or between one or morecomputing devices 500 associated with the billing record convertersystem 210. Referring now to FIG. 5, an example computing device 500 ofa billing record converter system 210 is presented. The computing device500 can be a server, and can be integrated with other systems orsubsystems, such as the 4G LTE network element 300 of FIG. 3. Othercomputing devices 500 are also contemplated, including but not limitedto stand-alone servers, cloud-based computing capability, and processesexecuting on the 4G LTE network element, other network elements, ormobile devices.

The computing device 500 can be any suitable computing device as wouldbe understood in the art, including without limitation, a custom chip,an embedded processing device, a desktop, a microcomputer, aminicomputer, a server, a mainframe, or any other suitable programmabledevice. In various embodiments disclosed herein, a single component canbe replaced by multiple components and multiple components can bereplaced by a single component to perform a given function or functions.Except where such substitution would not be operative, such substitutionis within the intended scope of the embodiments.

The computing device 500 includes a processor 502 that can be anysuitable type of processing unit, for example a general purpose centralprocessing unit (CPU), a reduced instruction set computer (RISC), aprocessor that has a pipeline or multiple processing capabilityincluding having multiple cores, a complex instruction set computer(CISC), a digital signal processor (DSP), an application specificintegrated circuits (ASIC), a programmable logic devices (PLD), and afield programmable gate array (FPGA), among others.

The computing device 500 also includes one or more memories 506, forexample read only memory (ROM), random access memory (RAM), cache memoryassociated with the processor 502, or other memories such as dynamic RAM(DRAM), static RAM (SRAM), programmable ROM (PROM), electricallyerasable PROM (EEPROM), flash memory, a removable memory card or disk, asolid state drive, and so forth. The computing device 500 also includesstorage media such as a storage device that can be configured to havemultiple modules, such as magnetic disk drives, floppy drives, tapedrives, hard drives, optical drives and media, magneto-optical drivesand media, Compact Disc (CD) drives, Compact Disc Read Only Memory(CD-ROM), Compact Disc Recordable (CD-R), Compact Disc Rewriteable(CD-RW), a suitable type of Digital Versatile Disc (DVD) or BluRay disc,and so forth. Storage media such as flash drives, solid state harddrives, redundant array of individual disks (RAID), virtual drives,networked drives and other memory means including storage media on theprocessor 502, or memories 506 are also contemplated as storage devices.It can be appreciated that such memory can be internal or external withrespect to operation of the disclosed embodiments. It can be appreciatedthat certain portions of the processes described herein can be performedusing instructions stored on a computer-readable medium or media thatdirect a computer system to perform the process steps. Non-transitorycomputer-readable media, as used herein, comprises all computer-readablemedia except for transitory, propagating signals.

If the computing device 500 is a blade server, or interface card, thatis configured to be inserted into, and reside in, a network element suchas a 4G LTE network element, then the computing device 500 can includebackplane interfaces 504. The backplane interfaces 504 can be configuredto communicate on one or more buses or communication channels on abackplane 514 of a network element. The signaling, power, and data linksof the backplane interfaces 504 can be proprietary and/or standardsbased. For example, backplane interfaces 504 can be based ontime-division multiplexing, telecom standards based interfaces such asSONET or synchronous optical network interfaces, or data communicationbased standards such as serial, parallel, X.25, Ethernet, TCP/IP,UDP/IP, IP, Frame Relay, ATM, and so forth. Other interfaces can also beused as would be understood by one of ordinary skill in the art. Thebackplane interfaces 504 can include one or more data links fortransmitting and/or receiving data from other modules of the networkelement.

In a configuration, the billing record converter system 210 is softwareexecuting on a blade server that inserts into, and resides in, a 4G LTEnetwork element or kit, which is often mounted in a 19-inch or 23-inchtelecom rack. In one embodiment, the 3GPP OCS records 208 are receivedfrom other modules of the 4G LTE network element over the backplane, forexample from the MME 302 of FIG. 3. In another embodiment the 3GPP OCSrecords 208 can be received through a network interface on the frontpanel of the blade server. The network interface can also be connectedvia wiring to a wiring panel associated with the 4G LTE network element.Similarly, in different embodiments, the TAP records 212 created by thebilling record converter system 210 can be output over the backplane 514to other modules of the 4G LTE network, or through network andcommunication interfaces 508 associated with the blade server. Otherways of receiving 3GPP OCS records 208 and transmitting TAP records 212can also be used, including but not limited to using other backplane ornetworking interfaces, using tunneling protocols, using wirelessprotocols, embedding TAP records 212 or information in other records orprotocols, and so forth.

The network and communication interfaces 508 can be configured totransmit to, or receive data from, other computing devices 500 across anetwork 512. For example, a remote billing system can receive TAPrecords 212 from the billing record converter system 210 over a networkor communications interface as described herein. The network andcommunication interfaces 508 can be an Ethernet interface, a radiointerface, a Universal Serial Bus (USB) interface, or any other suitablecommunications interface and can include receivers, transmitter, andtransceivers. For purposes of clarity, a transceiver can be referred toas a receiver or a transmitter when referring to only the input or onlythe output functionality of the transceiver. Example communicationinterfaces 508 can include wired data transmission links such asEthernet and TCP/IP. The communication interfaces 508 can includewireless protocols for interfacing with private or public networks 512.For example, the network and communication interfaces 508 and protocolscan include interfaces for communicating with private wireless networks512 such as a WiFi network, one of the IEEE 802.11x family of networks,or another suitable wireless network. The network and communicationinterfaces 508 can include interfaces and protocols for communicatingwith public wireless networks 512, using for example wireless protocolsused by cellular network providers, including Long Term Evolution (LTE),Code Division Multiple Access (CDMA) and Global System for MobileCommunications (GSM). The computing device 500 can use network andcommunication interfaces 508 to communicate with hardware modules suchas a database or data store, or one or more servers or other networkedcomputing resources. Data can be encrypted or protected fromunauthorized access.

In various configurations, the computing device 500 can include a systembus 510 for interconnecting the various components of the computingdevice 500, or the computing device 500 can be integrated into one ormore chips such as programmable logic device or application specificintegrated circuit (ASIC). The system bus 510 can include a memorycontroller, a local bus, or a peripheral bus for supporting input andoutput devices and network communication interfaces 508. Example inputand output devices (not shown) include keyboards, keypads, gesture orgraphical input devices, motion input devices, touchscreen interfaces,one or more displays, audio units, voice recognition units, vibratorydevices, computer mice, and any other suitable user interface.

The processor 502 and memory 506 can include nonvolatile memory forstoring computer-readable instructions, data, data structures, programmodules, code, microcode, and other software components for storing thecomputer-readable instructions in non-transitory computer-readablemediums in connection with the other hardware components for carryingout the methodologies described herein. Software components can includesource code, compiled code, interpreted code, executable code, staticcode, dynamic code, encrypted code, or any other suitable type of codeor computer instructions implemented using any suitable high-level,low-level, object-oriented, visual, compiled, or interpreted programminglanguage

Some of the figures can include a flow diagram. Although such figurescan include a particular logic flow, it can be appreciated that thelogic flow merely provides an exemplary implementation of the generalfunctionality. Further, the logic flow does not necessarily have to beexecuted in the order presented unless otherwise indicated. In addition,the logic flow can be implemented by a hardware element, a softwareelement executed by a computer, a firmware element embedded in hardware,or any combination thereof.

The foregoing description of embodiments and examples has been presentedfor purposes of illustration and description. It is not intended to beexhaustive or limiting to the forms described. Numerous modificationsare possible in light of the above teachings. Some of thosemodifications have been discussed, and others will be understood bythose skilled in the art. The embodiments were chosen and described inorder to best illustrate principles of various embodiments as are suitedto particular uses contemplated. The scope is, of course, not limited tothe examples set forth herein, but can be employed in any number ofapplications and equivalent devices by those of ordinary skill in theart. Rather it is hereby intended the scope of the invention to bedefined by the claims appended hereto.

The invention claimed is:
 1. A method of converting mobilecommunications network billing records, performed by a processor of abilling record converter system executing instructions stored in amemory, the method comprising: receiving a first data usage billingrecord associated with a mobile computing device communicatively coupledto a long term evolution (LTE) wireless communications network, thefirst data usage billing record is formatted according to a real-timedata usage billing record format; receiving, during a communicationssession, additional data usage billing records associated with themobile computing device communicatively coupled to the LTE wirelesscommunications network, the additional data usage billing records areformatted according to the real-time data usage billing record format;cumulating the first data usage billing record and the additional datausage billing records received during the communications session into acumulated data usage billing record formatted according to the real-timedata usage billing record format; determining an amount of data used bythe mobile computing device during the communications session based onthe first data usage billing record and the additional data usagebilling records received during the communications session; determiningwhether the determined amount of data used by the mobile computingdevice during the communications session satisfies a reference datausage threshold; converting, in response to a determination that thedetermined amount of data used by the mobile computing device satisfiesthe reference data usage threshold, the cumulated data usage billingrecord formatted according to the real-time data usage billing recordformat into a second data usage billing record formatted according to aroaming data usage record format, the roaming data usage record formatcorresponds to a legacy wireless communications network different fromthe LTE wireless communications network; and transmitting the seconddata usage billing record to a billing system of the legacy wirelesscommunications network for processing.
 2. The method of claim 1, whereinthe real-time data usage billing record format is a 3rd generationpartnership project online charging system format and the roaming datausage record format is a Transferred Account Procedure (TAP) format. 3.The method of claim 1, wherein the legacy wireless communicationsnetwork is a third generation (3G) wireless communications network. 4.The method of claim 1, wherein transmitting the second data usagebilling record to the billing system of the legacy wirelesscommunications network comprises transmitting the second data usagebilling record to a roaming data usage record exchanger of the legacywireless communications network for forwarding to the billing system. 5.The method of claim 1, further comprising: determining whether thecommunications session of the mobile computing device communicativelycoupled to the LTE wireless communications network has ended; andwherein converting the first data usage billing record into the seconddata usage billing record comprises converting, in response to adetermination that the determined amount of data used by the mobilecomputing device satisfies the reference data usage threshold and inresponse to a determination that the communications session has ended,the cumulated data usage billing record formatted according to thereal-time data usage billing record format into the second data usagebilling record formatted according to the roaming data usage recordformat.
 6. The method of claim 1, further comprising: determining apredicted amount of data to be used by the mobile computing deviceduring the communications session based at least in part on historicaldata usage patterns of the mobile computing device; and configuring thereference data usage threshold as a function of the predicted amount ofdata to be used by the mobile computing device during the communicationssession.
 7. The method of claim 1, further comprising: determining apredicted amount of data to be used by the mobile computing deviceduring the communications session based at least in part on historicaldata usage patterns of other mobile computing devices communicativelycoupled to the LTE wireless communications network; and configuring thereference data usage threshold as a function of the predicted amount ofdata to be used by the mobile computing device during the communicationssession.
 8. The method of claim 1, further comprising: determining atype of the communications session associated with first data usagebilling record and the additional data usage billing records; andmodifying the reference data usage threshold based at least in part onthe determined type of the communications session.
 9. The method ofclaim 1, further comprising: determining an amount of time elapsed forthe communications session; and modifying the reference data usagethreshold based at least in part on the determined amount of timeelapsed for the communications session.
 10. A system for convertingmobile communications network billing records, the system comprising: abilling record converter system comprising a processor executinginstructions stored in memory, wherein the instructions cause theprocessor of the billing record converter system to: receive a firstdata usage billing record associated with a mobile computing devicecommunicatively coupled to a long term evolution (LTE) wirelesscommunications network, the first data usage billing record is formattedaccording to a real-time data usage billing record format; receive,during a communications session, additional data usage billing recordsassociated with the mobile computing device communicatively coupled tothe LTE wireless communications network, the additional data usagebilling records are formatted according to the real-time data usagebilling record format; cumulate the first data usage billing record andthe additional data usage billing records received during thecommunications session into a cumulated data usage billing recordformatted according to the real-time data usage billing record format;determine an amount of data used by the mobile computing device duringthe communications session based on the first data usage billing recordand the additional data usage billing records received during thecommunications session; determine whether the determined amount of dataused by the mobile computing device during the communications sessionsatisfies a reference data usage threshold; convert, in response to adetermination that the determined amount of data used by the mobilecomputing device satisfies the reference data usage threshold, thecumulated data usage billing record formatted according to the real-timedata usage billing record format into a second data usage billing recordformatted according to a roaming data usage record format, the roamingdata usage record format corresponds to a legacy wireless communicationsnetwork different from the LTE wireless communications network; andtransmit the second data usage billing record to a billing system of thelegacy wireless communications network for processing.
 11. The system ofclaim 10, wherein the real-time data usage billing record format is a3rd generation partnership project online charging system format and theroaming data usage record format is a Transferred Account Procedure(TAP) format.
 12. The system of claim 10, wherein the legacy wirelesscommunications network is a third generation (3G) wirelesscommunications network.
 13. The system of claim 10, wherein to transmitthe second data usage billing record to the billing system of the legacywireless communications network comprises to transmit the second datausage billing record to a roaming data usage record exchanger of thelegacy wireless communications network for forwarding to the billingsystem.
 14. The system of claim 10, wherein the instructions of thebilling record converter system further cause the processor of thebilling record converter system to: determine whether the communicationssession of the mobile computing device communicatively coupled to theLTE wireless communications network has ended; and wherein to convertthe first data usage billing record into the second data usage billingrecord comprises to convert, in response to a determination that thedetermined amount of data used by the mobile computing device satisfiesthe reference data usage threshold and in response to a determinationthat the communications session has ended, the cumulated data usagebilling record formatted according to the real-time data usage billingrecord format into the second data usage billing record formattedaccording to the roaming data usage record format.
 15. The system ofclaim 10, wherein the instructions of the billing record convertersystem further cause the processor of the billing record convertersystem to: determine a predicted amount of data to be used by the mobilecomputing device during the communications session based at least inpart on historical data usage patterns of the mobile computing device;and configure the reference data usage threshold as a function of thepredicted amount of data to be used by the mobile computing deviceduring the communications session.
 16. The system of claim 10, whereinthe instructions of the billing record converter system further causethe processor of the billing record converter system to: determine apredicted amount of data to be used by the mobile computing deviceduring the communications session based at least in part on historicaldata usage patterns of other mobile computing devices communicativelycoupled to the LTE wireless communications network; and configure thereference data usage threshold as a function of the predicted amount ofdata to be used by the mobile computing device during the communicationssession.
 17. The system of claim 10, wherein the instructions of thebilling record converter system further cause the processor of thebilling record converter system to: determine a type of thecommunications session associated with first data usage billing recordand the additional data usage billing records; and modify the referencedata usage threshold based at least in part on the determined type ofthe communications session.
 18. The system of claim 10, wherein theinstructions of the billing record converter system further cause theprocessor of the billing record converter system to: determine an amountof time elapsed for the communications session; and modify the referencedata usage threshold based at least in part on the determined amount oftime elapsed for the communications session.